-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Allow reverting a range of commits #4444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
dfda949
to
d81bb8b
Compare
622baa9
to
e535935
Compare
d81bb8b
to
e30f7b4
Compare
e535935
to
81b1803
Compare
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferencesFootnotes
|
e30f7b4
to
3ff8f5c
Compare
81b1803
to
9a5e245
Compare
3ff8f5c
to
fb458bb
Compare
9a5e245
to
8aaacef
Compare
fb458bb
to
417080e
Compare
8aaacef
to
c711aa4
Compare
417080e
to
108054e
Compare
In pretty much 100% of the cases, you want to use -m1, so spare users the complexity of a confusing prompt. See https://public-inbox.org/git/[email protected]/ for some discussion.
It's only called from one place now, so there's no reason not to inline it.
c711aa4
to
945b023
Compare
This is part four of a four part series of PRs that improve the cherry-pick and revert experience.
With this PR we support reverting a range selection of commits.
Fixes #3272
go generate ./...
)